-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding axial top bottom margin to the cover block. #41963
Conversation
Regenerated docs
I think the improved visualiser, and limiting it to top and bottom margin answers the concerns from the previous PR. The confusion over collapsing margins is certainly made clearer with the visualiser at least showing the user that something is happening even of the blocks are not moving (top cover block below has a 40px bottom margin set, so any changes to gap won't happen until bottom covers top margin exceeds 40px): collapse.mp4I did hit a strange glitch with the visualiser when one cover is below another, but haven't managed to work out exactly how to replicate it yet, and probably not related to this PR: cover-margin.mp4 |
After a page refresh I wasn't able to replicate the issue noted above, so unless someone else sees the same thing we can probably ignore for now. |
Thanks for testing @glendaviesnz !
I had a go with several cover blocks stacked, and couldn't replicate (at least on my side) One thing I forgot to confirm is whether we can reduce the margin to 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I think improvements to the visualiser, along with limiting to top and bottom margins for now answers the issues raised in the previous iteration of this.
Added the Needs Dev Note label in case this needs a dev note (either individual or as part of a "misc" dev note) for WP 6.1 release. |
What?
Revives #33835 and fixes #41879 by bringing top and bottom margin controls to the cover block:
Why?
Previous attempts to add this control were put in doubt due to the unavailability of the visualizer. It looks like the visualizer is looking better since #40505
How?
Via block.json
Testing Instructions